Skip to content

Conversation

AdmiralSnyder
Copy link
Contributor

also: when the docs page's version is changed to e.g. 4.7.1 the hint for the nuget package should be visible instead of forwarding to core 3.1 and saying it's not available...

when the docs page's version is changed to e.g. 4.7.1 the hint for the nuget package should be visible instead of forwarding to core 3.1 and saying it's not available...
@dotnet-bot dotnet-bot added this to the February 2020 milestone Feb 20, 2020
@Thraka
Copy link
Contributor

Thraka commented Feb 26, 2020

@docs-product thoughts?

Hi @AdmiralSnyder. Thank you for opening this PR. I know you're trying to solve a problem with how the site displays this information, IE you can't figure out the fact that the NuGet package contains this class and it's not just available on the system by default. We have a much larger problem with displaying this information. This is something we would rather get fixed by the site (such as automatically listing the nuget packages per class) rather than note in text that we would eventually have to remove.

@BillWagner
Copy link
Member

I'm closing this.

@AdmiralSnyder We do have a plan to display the NuGet package that contains a type throughout the API site. That will fix this issue, and fix it across all types in .NET.

@BillWagner BillWagner closed this Mar 2, 2020
@AdmiralSnyder
Copy link
Contributor Author

thanks :-) . knowing there's gonna be a solution for this general issue is helpful. is there something i can bookmark to get info for when it's in place?

also: should i better have created an issue instead?

@Thraka
Copy link
Contributor

Thraka commented Mar 6, 2020

@AdmiralSnyder I don't believe there is anything public tracking that work. Just be assured we're well aware and have raised this to the docs team so it's on the plan and in flight. No ETA though.

Issues are really useful when you have a lot of work that you want to discuss and get approved, or just get feedback on before starting the work. Doing a lot of work and then getting it denied sucks 😄 but something like this is minor and doesn't take you a ton of time so it's not really terrible if it gets denied, you're not out a lot of time and effort. We really want to protect contributors time, we really appreciate all the work you do to helping make docs better. So thanks!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants